Yesterday I flew two approaches with my GNS 430, the RNAV (GPS) RWY 03
at KCHO, and the RNAV (GPS) RWY 24 at KROA. In both cases, the 430
reported "Approach Not Active" just s I reached the FAF (JAGAG at CHO
and HIBAN at ROA), and stopped sequencing. I am quite certain that I
activated both approaches when I added them to the flight plan (not
just "Loaded" them). It was VMC+ at each airport, so I just continued
to landing both times. I didn't get any other warnings or messages
from the 430.

Any ideas on why the 430 may have stopped sequencing at the FAF on my
approaches?

I re-read the Pilot's Guide, but if there's something related there I
didn't see it.

Thanks,
Dave

RAIM failure?

David wrote:
> Yesterday I flew two approaches with my GNS 430, the RNAV (GPS) RWY 03
> at KCHO, and the RNAV (GPS) RWY 24 at KROA. In both cases, the 430
> reported "Approach Not Active" just s I reached the FAF (JAGAG at CHO
> and HIBAN at ROA), and stopped sequencing. I am quite certain that I
> activated both approaches when I added them to the flight plan (not
> just "Loaded" them). It was VMC+ at each airport, so I just continued
> to landing both times. I didn't get any other warnings or messages
> from the 430.
>
> Any ideas on why the 430 may have stopped sequencing at the FAF on my
> approaches?
>
> I re-read the Pilot's Guide, but if there's something related there I
> didn't see it.
>
> Thanks,
> Dave

Were you being vectored to the final approach course? If so, you need
to be established on the FAC at least two miles prior to the FAP. If
you're not established two miles out from the FAP, the approach mode
will not activate.

That's somewhere in the book, and I've seen it myself.

On 4 Jun 2004 20:38:57 -0700, (David) wrote:

>Yesterday I flew two approaches with my GNS 430, the RNAV (GPS) RWY 03
>at KCHO, and the RNAV (GPS) RWY 24 at KROA. In both cases, the 430
>reported "Approach Not Active" just s I reached the FAF (JAGAG at CHO
>and HIBAN at ROA), and stopped sequencing. I am quite certain that I
>activated both approaches when I added them to the flight plan (not
>just "Loaded" them). It was VMC+ at each airport, so I just continued
>to landing both times. I didn't get any other warnings or messages
>from the 430.
>
>Any ideas on why the 430 may have stopped sequencing at the FAF on my
>approaches?
>
>I re-read the Pilot's Guide, but if there's something related there I
>didn't see it.
>
>Thanks,
>Dave

David wrote:

> Yesterday I flew two approaches with my GNS 430, the RNAV (GPS) RWY 03
> at KCHO, and the RNAV (GPS) RWY 24 at KROA. In both cases, the 430
> reported "Approach Not Active" just s I reached the FAF (JAGAG at CHO
> and HIBAN at ROA), and stopped sequencing. I am quite certain that I
> activated both approaches when I added them to the flight plan (not
> just "Loaded" them). It was VMC+ at each airport, so I just continued
> to landing both times. I didn't get any other warnings or messages
> from the 430.
>
> Any ideas on why the 430 may have stopped sequencing at the FAF on my
> approaches?

The message means what it says. Go to the procedures page and activate
the approach. This will activate any approach except for a RAIM failure
and you would know that by a separate message.

wrote:

> Were you being vectored to the final approach course? If so, you need
> to be established on the FAC at least two miles prior to the FAP. If
> you're not established two miles out from the FAP, the approach mode
> will not activate.

Perhaps not, automatically. But, if you go to the procedures page and
activate, it will activate, period (excepting for RAIM failure).

No vectors, I was on course, on the flight plan, each time.

The previous post questioning RAIM failure makes me think that is the
likely suspect. I didn't think to check the status screen right at
that time (too busy flying), but if this happens again I will take a
closer look if at all possible.

Dave

wrote in message >...
> Were you being vectored to the final approach course? If so, you need
> to be established on the FAC at least two miles prior to the FAP. If
> you're not established two miles out from the FAP, the approach mode
> will not activate.
>
> That's somewhere in the book, and I've seen it myself.
>
> On 4 Jun 2004 20:38:57 -0700, (David) wrote:
>
> >Yesterday I flew two approaches with my GNS 430, the RNAV (GPS) RWY 03
> >at KCHO, and the RNAV (GPS) RWY 24 at KROA. In both cases, the 430
> >reported "Approach Not Active" just s I reached the FAF (JAGAG at CHO
> >and HIBAN at ROA), and stopped sequencing. I am quite certain that I
> >activated both approaches when I added them to the flight plan (not
> >just "Loaded" them). It was VMC+ at each airport, so I just continued
> >to landing both times. I didn't get any other warnings or messages
> >from the 430.
> >
> >Any ideas on why the 430 may have stopped sequencing at the FAF on my
> >approaches?
> >
> >I re-read the Pilot's Guide, but if there's something related there I
> >didn't see it.
> >
> >Thanks,
> >Dave

Hi David,

There are couple of possibilities. One is a RAIM error. If a RAIM issue
occurs at the FAF you will get that message, followed by another message
saying that RAIM was not available. The second possibility is that your
unit was in Suspend mode and no longer automatically sequencing waypoints.
This would have occured back at the IAF. The chart shows that KENNI is the
IAF for the approach at KCHO. It is also the holding fix. Therefore, when
you arrived at KENNI the GNS 430 would have automatically gone into suspend
mode, since the unit could not know whether you were going to hold or
continue. The message "SUSP" should have been displayed above the OBS
button. If you press the OBS button the automatic sequencing will continue
from KENNI inbound. I have seen a number of people tripped up by the
auto-suspend "feature" of the GNS radios.

jerry


"David" > wrote in message
om...
> Yesterday I flew two approaches with my GNS 430, the RNAV (GPS) RWY 03
> at KCHO, and the RNAV (GPS) RWY 24 at KROA. In both cases, the 430
> reported "Approach Not Active" just s I reached the FAF (JAGAG at CHO
> and HIBAN at ROA), and stopped sequencing. I am quite certain that I
> activated both approaches when I added them to the flight plan (not
> just "Loaded" them). It was VMC+ at each airport, so I just continued
> to landing both times. I didn't get any other warnings or messages
> from the 430.
>
> Any ideas on why the 430 may have stopped sequencing at the FAF on my
> approaches?
>
> I re-read the Pilot's Guide, but if there's something related there I
> didn't see it.
>
> Thanks,
> Dave

My 430 will ask me if I want to HOLD.


"Jerry Kurata" > wrote in message
...
> Hi David,
>
> There are couple of possibilities. One is a RAIM error. If a RAIM issue
> occurs at the FAF you will get that message, followed by another message
> saying that RAIM was not available. The second possibility is that your
> unit was in Suspend mode and no longer automatically sequencing waypoints.
> This would have occured back at the IAF. The chart shows that KENNI is
the
> IAF for the approach at KCHO. It is also the holding fix. Therefore,
when
> you arrived at KENNI the GNS 430 would have automatically gone into
suspend
> mode, since the unit could not know whether you were going to hold or
> continue. The message "SUSP" should have been displayed above the OBS
> button. If you press the OBS button the automatic sequencing will continue
> from KENNI inbound. I have seen a number of people tripped up by the
> auto-suspend "feature" of the GNS radios.
>
> jerry
>
>
> "David" > wrote in message
> om...
> > Yesterday I flew two approaches with my GNS 430, the RNAV (GPS) RWY 03
> > at KCHO, and the RNAV (GPS) RWY 24 at KROA. In both cases, the 430
> > reported "Approach Not Active" just s I reached the FAF (JAGAG at CHO
> > and HIBAN at ROA), and stopped sequencing. I am quite certain that I
> > activated both approaches when I added them to the flight plan (not
> > just "Loaded" them). It was VMC+ at each airport, so I just continued
> > to landing both times. I didn't get any other warnings or messages
> > from the 430.
> >
> > Any ideas on why the 430 may have stopped sequencing at the FAF on my
> > approaches?
> >
> > I re-read the Pilot's Guide, but if there's something related there I
> > didn't see it.
> >
> > Thanks,
> > Dave
>
>

I think Jerry's second possibility may be the cause. I was tripped up by
this too. I now include "Remove Hold......Consider" in my approach checklist
as a result.

Marco

"Jerry Kurata" > wrote in message
...
> Hi David,
>
> There are couple of possibilities. One is a RAIM error. If a RAIM issue
> occurs at the FAF you will get that message, followed by another message
> saying that RAIM was not available. The second possibility is that your
> unit was in Suspend mode and no longer automatically sequencing waypoints.
> This would have occured back at the IAF. The chart shows that KENNI is
the
> IAF for the approach at KCHO. It is also the holding fix. Therefore,
when
> you arrived at KENNI the GNS 430 would have automatically gone into
suspend
> mode, since the unit could not know whether you were going to hold or
> continue. The message "SUSP" should have been displayed above the OBS
> button. If you press the OBS button the automatic sequencing will continue
> from KENNI inbound. I have seen a number of people tripped up by the
> auto-suspend "feature" of the GNS radios.
>
> jerry
>
>
> "David" > wrote in message
> om...
> > Yesterday I flew two approaches with my GNS 430, the RNAV (GPS) RWY 03
> > at KCHO, and the RNAV (GPS) RWY 24 at KROA. In both cases, the 430
> > reported "Approach Not Active" just s I reached the FAF (JAGAG at CHO
> > and HIBAN at ROA), and stopped sequencing. I am quite certain that I
> > activated both approaches when I added them to the flight plan (not
> > just "Loaded" them). It was VMC+ at each airport, so I just continued
> > to landing both times. I didn't get any other warnings or messages
> > from the 430.
> >
> > Any ideas on why the 430 may have stopped sequencing at the FAF on my
> > approaches?
> >
> > I re-read the Pilot's Guide, but if there's something related there I
> > didn't see it.
> >
> > Thanks,
> > Dave
>
>



Posted Via Usenet.com Premium Usenet Newsgroup Services
----------------------------------------------------------
** SPEED ** RETENTION ** COMPLETION ** ANONYMITY **
----------------------------------------------------------
http://www.usenet.com

wrote:

> Were you being vectored to the final approach course? If so, you need
> to be established on the FAC at least two miles prior to the FAP. If
> you're not established two miles out from the FAP, the approach mode
> will not activate.

It will unless the intercept angle is really ugly. Garmin doesn't define
the limits. The approach mode will also drop out inside the FAF if you
turn significantly away from the approach track.

"David" > wrote in message
om...
> Yesterday I flew two approaches with my GNS 430, the RNAV (GPS) RWY 03
> at KCHO, and the RNAV (GPS) RWY 24 at KROA. In both cases, the 430
> reported "Approach Not Active" just s I reached the FAF (JAGAG at CHO

This is exactly what happened on a CFIT accident at RHV with a new IFR pilot
in a Cirrus. Instead of flying to the MAP and executing the missed, the
pilot his PROC-Active Approach and it took him back to the IAF.

--------------------
Richard Kaplan, CFII

www.flyimc.com